View AM29F160BB-120WCC_8305986.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

preliminary publication# 21358 rev: f amendment/ +2 issue date: march 1998 am29lv160b 16 megabit (2 m x 8-bit/1 m x 16-bit) cmos 3.0 volt-only boot sector flash memory distinctive characteristics n single power supply operation full voltage range: 2.7 to 3.6 volt read and write operations for battery-powered applications regulated voltage range: 3.0 to 3.6 volt read and write operations and for compatibility with high performance 3.3 volt microprocessors n manufactured on 0.35 m process technology n supports common flash memory interface (cfi) n high performance full voltage range: access times as fast as 90 ns regulated voltage range: access times as fast as 80 ns n ultra low power consumption (typical values at 5 mhz) 200 na automatic sleep mode current 200 na standby mode current 9 ma read current 20 ma program/erase current n flexible sector architecture one 16 kbyte, two 8 kbyte, one 32 kbyte, and thirty-one 64 kbyte sectors (byte mode) one 8 kword, two 4 kword, one 16 kword, and thirty-one 32 kword sectors (word mode) supports full chip erase sector protection features: a hardware method of locking a sector to prevent any program or erase operations within that sector sectors can be locked in-system or via programming equipment temporary sector unprotect feature allows code changes in previously locked sectors n unlock bypass program command reduces overall programming time when issuing multiple program command sequences n top or bottom boot block configurations available n embedded algorithms embedded erase algorithm automatically preprograms and erases the entire chip or any combination of designated sectors embedded program algorithm automatically writes and verifies data at specified addresses n minimum 1,000,000 write cycle guarantee per sector n package option 48-ball fbga 48-pin tsop 44-pin so n cfi (common flash interface) compliant provides device-specific information to the system, allowing host software to easily reconfigure for different flash devices n compatibility with jedec standards pinout and software compatible with single- power supply flash superior inadvertent write protection n data# polling and toggle bits provides a software method of detecting program or erase operation completion n ready/busy# pin (ry/by#) provides a hardware method of detecting program or erase cycle completion (not available on 44-pin so) n erase suspend/erase resume suspends an erase operation to read data from, or program data to, a sector that is not being erased, then resumes the erase operation n hardware reset pin (reset#) hardware method to reset the device to reading array data
preliminary 2 am29lv160b general description the am29lv160b is a 16 mbit, 3.0 volt-only flash memory organized as 2,097,152 bytes or 1,048,576 words. the device is offered in 48-ball fbga, 44-pin so, and 48-pin tsop packages. the word-wide data (x16) appears on dq15Cdq0; the byte-wide (x8) data appears on dq7Cdq0. this device is designed to be programmed in-system with the standard system 3.0 volt v cc supply. a 12.0 v v pp or 5.0 v cc are not required for write or erase operations. the device can also be programmed in standard eprom programmers. the device offers access times of 80, 90, and 120 ns, allowing high speed microprocessors to operate without wait states. to eliminate bus contention the device has separate chip enable (ce#), write enable (we#) and output enable (oe#) controls. the device requires only a single 3.0 volt power sup- ply for both read and write functions. internally gener- ated and regulated voltages are provided for the program and erase operations. the am29lv160b is entirely command set compatible with the jedec single-power-supply flash standard . commands are written to the command reg- ister using standard microprocessor write timings. reg- ister contents serve as input to an internal state- machine that controls the erase and programming cir- cuitry. write cycles also internally latch addresses and data needed for the programming and erase opera- tions. reading data out of the device is similar to reading from other flash or eprom devices. device programming occurs by executing the program command sequence. this initiates the embedded program algorithman internal algorithm that auto- matically times the program pulse widths and verifies proper cell margin. the unlock bypass mode facili- tates faster programming times by requiring only two write cycles to program data instead of four. device erasure occurs by executing the erase com- mand sequence. this initiates the embedded erase algorithman internal algorithm that automatically pre- programs the array (if it is not already programmed) be- fore executing the erase operation. during erase, the device automatically times the erase pulse widths and verifies proper cell margin. the host system can detect whether a program or erase operation is complete by observing the ry/by# pin, or by reading the dq7 (data# polling) and dq6 (toggle) status bits . after a program or erase cycle has been completed, the device is ready to read array data or accept another command. the sector erase architecture allows memory sectors to be erased and reprogrammed without affecting the data contents of other sectors. the device is fully erased when shipped from the factory. hardware data protection measures include a low v cc detector that automatically inhibits write operations dur- ing power transitions. the hardware sector protection feature disables both program and erase operations in any combination of the sectors of memory. this can be achieved in-system or via programming equipment. the erase suspend/erase resume feature enables the user to put erase on hold for any period of time to read data from, or program data to, any sector that is not selected for erasure. true background erase can thus be achieved. the hardware reset# pin terminates any operation in progress and resets the internal state machine to reading array data. the reset# pin may be tied to the system reset circuitry. a system reset would thus also reset the device, enabling the system microprocessor to read the boot-up firmware from the flash memory. the device offers two power-saving features. when addresses have been stable for a specified amount of time, the device enters the automatic sleep mode . the system can also place the device into the standby mode . power consumption is greatly reduced in both these modes. amds flash technology combines years of flash memory manufacturing experience to produce the highest levels of quality, reliability and cost effectiveness. the device electrically erases all bits within a sector simultaneously via fowler-nordheim t unneling. the data is programmed using hot electron injection.
preliminary am29lv160b 3 product selector guide note: see ac characteristics for full specifications. block diagram family part number am29lv160b speed option regulated voltage range: v cc =3.0C3.6 v 80r full voltage range: v cc = 2.7C3.6 v 90 120 max access time, ns (t acc ) 80 90 120 max ce# access time, ns (t ce ) 80 90 120 max oe# access time, ns (t oe ) 30 35 50 input/output buffers x-decoder y-decoder chip enable output enable logic erase voltage generator pgm voltage generator timer v cc detector state control command register v cc v ss we# byte# ce# oe# stb stb dq0 C dq15 (a-1) sector switches ry/by# reset# data latch y-gating cell matrix address latch a0Ca19 21358f-1
preliminary 4 am29lv160b connection diagrams a1 a15 a18 a14 a13 a12 a11 a10 a9 a8 a19 nc we# reset# nc nc ry/by# a17 a7 a6 a5 a4 a3 a2 1 16 2 3 4 5 6 7 8 17 18 19 20 21 22 23 24 9 10 11 12 13 14 15 a16 dq2 byte# v ss dq15/a-1 dq7 dq14 dq6 dq13 dq9 dq1 dq8 dq0 oe# v ss ce# a0 dq5 dq12 dq4 v cc dq11 dq3 dq10 48 33 47 46 45 44 43 42 41 40 39 38 37 36 35 34 25 32 31 30 29 28 27 26 a1 a15 a18 a14 a13 a12 a11 a10 a9 a8 a19 nc we# reset# nc nc ry/by# a17 a7 a6 a5 a4 a3 a2 1 16 2 3 4 5 6 7 8 17 18 19 20 21 22 23 24 9 10 11 12 13 14 15 a16 dq2 byte# v ss dq15/a-1 dq7 dq14 dq6 dq13 dq9 dq1 dq8 dq0 oe# v ss ce# a0 dq5 dq12 dq4 v cc dq11 dq3 dq10 48 33 47 46 45 44 43 42 41 40 39 38 37 36 35 34 25 32 31 30 29 28 27 26 21358f-2 reverse tsop standard tsop
preliminary am29lv160b 5 connection diagrams special handling instructions special handling is required for flash memory products in fbga packages. flash memory devices in fbga packages may be damaged if exposed to ultrasonic cleaning methods. the package and/or data integrity may be compromised if the package body is exposed to temperatures above 150 c for prolonged periods of time. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 reset# a18 a17 a7 a6 a5 a4 a3 a2 a1 a0 ce# v ss oe# dq0 dq8 dq1 dq9 dq2 dq10 dq3 dq11 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 we# a19 a8 a9 a10 a11 a12 a13 a14 a15 a16 byte# v ss dq15/a-1 dq7 dq14 dq6 dq13 dq5 dq12 dq4 v cc so 21358f-3 a1 b1 c1 d1 e1 f1 g1 h1 a2 b2 c2 d2 e2 f2 g2 h2 a3 b3 c3 d3 e3 f3 g3 h3 a4 b4 c4 d4 e4 f4 g4 h4 a5 b5 c5 d5 e5 f5 g5 h5 a6 b6 c6 d6 e6 f6 g6 h6 dq15/a-1 v ss byte# a16 a15 a14 a12 a13 dq13 dq6 dq14 dq7 a11 a10 a8 a9 v cc dq4 dq12 dq5 a19 nc reset# we# dq11 dq3 dq10 dq2 nc a18 nc ry/by# dq9 dq1 dq8 dq0 a5 a6 a17 a7 oe# v ss ce# a0 a1 a2 a4 a3 fbga bottom view 21358f-1
preliminary 6 am29lv160b pin configuration a0Ca19 = 20 addresses dq0Cdq14 = 15 data inputs/outputs dq15/a-1 = dq15 (data input/output, word mode), a-1 (lsb address input, byte mode) byte# = selects 8-bit or 16-bit mode ce# = chip enable oe# = output enable we# = write enable reset# = hardware reset pin ry/by# = ready/busy output (n/a so 044) v cc = 3.0 volt-only single power supply (see product selector guide for speed options and voltage supply tolerances) v ss = device ground nc = pin not connected internally logic symbol 21358f-4 20 16 or 8 dq0Cdq15 (a-1) a0Ca19 ce# oe# we# reset# byte# ry/by# (n/a so 044)
preliminary am29lv160b 7 ordering information standard products amd standard products are available in several packages and operating ranges. the order number (valid combi- nation) is formed by a combination of the elements below. valid combinations valid combinations list configurations planned to be sup- ported in volume for this device. consult the local amd sales office to confirm availability of specific valid combinations and to check on newly released combinations. device number/description am29lv160b 16 megabit (2m x 8-bit/1m x 16-bit) cmos flash memory 3.0 volt-only read, program, and erase c e 80r am29lv160b t optional processing blank = standard processing b = burn-in (contact an amd representative for more information) temperature range c= commercial (0c to +70c) i = industrial (C40c to +85c) e = extended (C55c to +125c) package type e = 48-pin thin small outline package (tsop) standard pinout (ts 048) f = 48-pin thin small outline package (tsop) reverse pinout (tsr048) s = 44-pin small outline package (so 044) wc = 48-ball fine-pitch ball grid array (fbga) 0.80 mm pitch, 8 x 9 mm package speed option see product selector guide and valid combinations boot code sector architecture t = top sector b = bottom sector valid combinations am29lv160bt80r, am29lv160bb80r ec, fc, sc, wcc am29lv160bt90, am29lv160bb90 ec, ei, ee, fc, fi, fe, sc, si, se, wcc, wci, wce am29lv160bt120, am29lv160bb120
preliminary 8 am29lv160b device bus operations this section describes the requirements and use of the device bus operations, which are initiated through the internal command register. the command register itself does not occupy any addressable memory location. the register is composed of latches that store the com- mands, along with the address and data information needed to execute the command. the contents of the register serve as inputs to the internal state machine. the state machine outputs dictate the function of the device. table 1 lists the device bus operations, the in- puts and control levels they require, and the resulting output. the following subsections describe each of these operations in further detail. table 1. am29lv160b device bus operations legend: l = logic low = v il , h = logic high = v ih , v id = 12.0 0.5 v, x = dont care, a in = address in, d in = data in, d out = data out notes: 1. addresses are a19:a0 in word mode (byte# = v ih ), a19:a-1 in byte mode (byte# = v il ). 2. the sector protect and sector unprotect functions may also be implemented via programming equipment. see the sector protection/unprotection section. word/byte configuration the byte# pin controls whether the device data i/o pins dq15Cdq0 operate in the byte or word configura- tion. if the byte# pin is set at logic 1, the device is in word configuration, dq15Cdq0 are active and control- led by ce# and oe#. if the byte# pin is set at logic 0, the device is in byte configuration, and only data i/o pins dq0Cdq7 are ac- tive and controlled by ce# and oe#. the data i/o pins dq8Cdq14 are tri-stated, and the dq15 pin is used as an input for the lsb (a-1) address function. requirements for reading array data to read array data from the outputs, the system must drive the ce# and oe# pins to v il . ce# is the power control and selects the device. oe# is the output control and gates array data to the output pins. we# should re- main at v ih . the byte# pin determines whether the de- vice outputs array data in words or bytes. the internal state machine is set for reading array data upon device power-up, or after a hardware reset. this ensures that no spurious alteration of the mem- ory content occurs during the power transition. no command is necessary in this mode to obtain array data. standard microprocessor read cycles that as- sert valid addresses on the device address inputs pro- duce valid data on the device data outputs. the device remains enabled for read access until the com- mand register contents are altered. see reading array data for more information. refer to the ac read operations table for timing specifica- tions and to figure 13 for the timing diagram. i cc1 in the dc characteristics table represents the active cur- rent specification for reading array data. operation ce# oe# we# reset# addresses (note 1) dq0C dq7 dq8Cdq15 byte# = v ih byte# = v il read l l h h a in d out d out dq8Cdq14 = high-z, dq15 = a-1 write l h l h a in d in d in standby v cc 0.3 v xx v cc 0.3 v x high-z high-z high-z output disable l h h h x high-z high-z high-z reset x x x l x high-z high-z high-z sector protect (note 2) l h l v id sector address, a6 = l, a1 = h, a0 = l d in xx sector unprotect (note 2) l h l v id sector address, a6 = h, a1 = h, a0 = l d in xx temporary sector unprotect xxx v id a in d in d in high-z
preliminary am29lv160b 9 writing commands/command sequences to write a command or command sequence (which in- cludes programming data to the device and erasing sectors of memory), the system must drive we# and ce# to v il , and oe# to v ih . for program operations, the byte# pin determines whether the device accepts program data in bytes or words. refer to word/byte configuration for more information. the device features an unlock bypass mode to facili- tate faster programming. once the device enters the un- lock bypass mode, only two write cycles are required to program a word or byte, instead of four. the word/byte program command sequence section has details on programming data to the device using both standard and unlock bypass command sequences. an erase operation can erase one sector, multiple sec- tors, or the entire device. tables 2 and 3 indicate the address space that each sector occupies. a sector ad- dress consists of the address bits required to uniquely select a sector. the command definitions section has details on erasing a sector or the entire chip, or suspending/resuming the erase operation. after the system writes the autoselect command se- quence, the device enters the autoselect mode. the system can then read autoselect codes from the inter- nal register (which is separate from the memory array) on dq7Cdq0. standard read cycle timings apply in this mode. refer to the autoselect mode and autoselect command sequence sections for more information. i cc2 in the dc characteristics table represents the ac- tive current specification for the write mode. the ac characteristics section contains timing specification tables and timing diagrams for write operations. program and erase operation status during an erase or program operation, the system may check the status of the operation by reading the status bits on dq7Cdq0. standard read cycle timings and i cc read specifications apply. refer to write operation status for more information, and to ac characteris- tics for timing diagrams. standby mode when the system is not reading or writing to the device, it can place the device in the standby mode. in this mode, current consumption is greatly reduced, and the outputs are placed in the high impedance state, inde- pendent of the oe# input. the device enters the cmos standby mode when the ce# and reset# pins are both held at v cc 0.3 v. (note that this is a more restricted voltage range than v ih .) if ce# and reset# are held at v ih , but not within v cc 0.3 v, the device will be in the standby mode, but the standby current will be greater. the device requires standard access time (t ce ) for read access when the device is in either of these standby modes, before it is ready to read data. if the device is deselected during erasure or program- ming, the device draws active current until the operation is completed. in the dc characteristics table, i cc3 and i cc4 repre- sents the standby current specification. automatic sleep mode the automatic sleep mode minimizes flash device energy consumption. the device automatically enables this mode when addresses remain stable for t acc + 30 ns. the automatic sleep mode is independent of the ce#, we#, and oe# control signals. standard address access timings provide new data when addresses are changed. while in sleep mode, output data is latched and always available to the system. i cc4 in the dc characteristics table represents the automatic sleep mode current specification.
preliminary 10 am29lv160b reset#: hardware reset pin the reset# pin provides a hardware method of reset- ting the device to reading array data. when the system drives the reset# pin to v il for at least a period of t rp , the device immediately terminates any operation in progress, tristates all data output pins, and ignores all read/write attempts for the duration of the reset# pulse. the device also resets the internal state ma- chine to reading array data. the operation that was in- terrupted should be reinitiated once the device is ready to accept another command sequence, to ensure data integrity. current is reduced for the duration of the reset# pulse. when reset# is held at v ss 0.3 v, the device draws cmos standby current (i cc4 ). if reset# is held at v il but not within v ss 0.3 v, the standby current will be greater. the reset# pin may be tied to the system reset cir- cuitry. a system reset would thus also reset the flash memory, enabling the system to read the boot-up firmware from the flash memory. if reset# is asserted during a program or erase op- eration, the ry/by# pin remains a 0 (busy) until the internal reset operation is complete, which requires a time of t ready (during embedded algorithms). the system can thus monitor ry/by# to determine whether the reset operation is complete. if reset# is asserted when a program or erase operation is not ex- ecuting (ry/by# pin is 1), the reset operation is completed within a time of t ready (not during embed- ded algorithms). the system can read data t rh after the reset# pin returns to v ih . refer to the ac characteristics tables for reset# pa- rameters and to figure 14 for the timing diagram. output disable mode when the oe# input is at v ih , output from the device is disabled. the output pins are placed in the high imped- ance state.
preliminary am29lv160b 11 table 2. sector address tables (am29lv160bt) note: address range is a19:a-1 in byte mode and a19:a0 in word mode. see word/byte configuration section for more information. sector a19 a18 a17 a16 a15 a14 a13 a12 sector size (kbytes/ kwords) address range (in hexadecimal) byte mode (x8) word mode (x16) sa0 0 0 0 0 0 x x x 64/32 000000C00ffff 00000C07fff sa1 0 0 0 0 1 x x x 64/32 010000C01ffff 08000C0ffff sa2 0 0 0 1 0 x x x 64/32 020000C02ffff 10000C17fff sa3 0 0 0 1 1 x x x 64/32 030000C03ffff 18000C1ffff sa4 0 0 1 0 0 x x x 64/32 040000C04ffff 20000C27fff sa5 0 0 1 0 1 x x x 64/32 050000C05ffff 28000C2ffff sa6 0 0 1 1 0 x x x 64/32 060000C06ffff 30000C37fff sa7 0 0 1 1 1 x x x 64/32 070000C07ffff 38000C3ffff sa8 0 1 0 0 0 x x x 64/32 080000C08ffff 40000C47fff sa9 0 1 0 0 1 x x x 64/32 090000C09ffff 48000C4ffff sa10 0 1 0 1 0 x x x 64/32 0a0000C0affff 50000C57fff sa11 0 1 0 1 1 x x x 64/32 0b0000C0bffff 58000C5ffff sa12 0 1 1 0 0 x x x 64/32 0c0000C0cffff 60000C67fff sa13 0 1 1 0 1 x x x 64/32 0d0000C0dffff 68000C6ffff sa14 0 1 1 1 0 x x x 64/32 0e0000C0effff 70000C77fff sa15 0 1 1 1 1 x x x 64/32 0f0000C0fffff 78000C7ffff sa16 1 0 0 0 0 x x x 64/32 100000C10ffff 80000C87fff sa17 1 0 0 0 1 x x x 64/32 110000C11ffff 88000C8ffff sa18 1 0 0 1 0 x x x 64/32 120000C12ffff 90000C97fff sa19 1 0 0 1 1 x x x 64/32 130000C13ffff 98000C9ffff sa20 1 0 1 0 0 x x x 64/32 140000C14ffff a0000Ca7fff sa21 1 0 1 0 1 x x x 64/32 150000C15ffff a8000Caffff sa22 1 0 1 1 0 x x x 64/32 160000C16ffff b0000Cb7fff sa23 1 0 1 1 1 x x x 64/32 170000C17ffff b8000Cbffff sa24 1 1 0 0 0 x x x 64/32 180000C18ffff c0000Cc7fff sa25 1 1 0 0 1 x x x 64/32 190000C19ffff c8000Ccffff sa26 1 1 0 1 0 x x x 64/32 1a0000C1affff d0000Cd7fff sa27 1 1 0 1 1 x x x 64/32 1b0000C1bffff d8000Cdffff sa28 1 1 1 0 0 x x x 64/32 1c0000C1cffff e0000Ce7fff sa29 1 1 1 0 1 x x x 64/32 1d0000C1dffff e8000Ceffff sa30 1 1 1 1 0 x x x 64/32 1e0000C1effff f0000Cf7fff sa31 1 1 1 1 1 0 x x 32/16 1f0000C1f7fff f8000Cfbfff sa32 1 1 1 1 1 1 0 0 8/4 1f8000C1f9fff fc000Cfcfff sa33 1 1 1 1 1 1 0 1 8/4 1fa000C1fbfff fd000Cfdfff sa34 1 1 1 1 1 1 1 x 16/8 1fc000C1fffff fe000Cfffff
preliminary 12 am29lv160b table 3. sector address tables (am29lv160bb) note: address range is a19:a-1 in byte mode and a19:a0 in word mode. see word/byte configuration section for more information. sector a19 a18 a17 a16 a15 a14 a13 a12 sector size (kbytes/ kwords) address range (in hexadecimal) byte mode (x8) word mode (x16) sa0 0000000x 16/8 000000C003fff 00000C01fff sa1 00000010 8/4 004000C005fff 02000C02fff sa2 00000011 8/4 006000C007fff 03000C03fff sa3 000001xx 32/16 008000C00ffff 04000C07fff sa4 00001xxx 64/32 010000C01ffff 08000C0ffff sa5 00010xxx 64/32 020000C02ffff 10000C17fff sa6 00011xxx 64/32 030000C03ffff 18000C1ffff sa7 00100xxx 64/32 040000C04ffff 20000C27fff sa8 00101xxx 64/32 050000C05ffff 28000C2ffff sa9 00110xxx 64/32 060000C06ffff 30000C37fff sa1000111xxx 64/32 070000C07ffff 38000C3ffff sa1101000xxx 64/32 080000C08ffff 40000C47fff sa1201001xxx 64/32 090000C09ffff 48000C4ffff sa1301010xxx 64/32 0a0000C0affff 50000C57fff sa1401011xxx 64/32 0b0000C0bffff 58000C5ffff sa1501100xxx 64/32 0c0000C0cffff 60000C67fff sa1601101xxx 64/32 0d0000C0dffff 68000C6ffff sa1701110xxx 64/32 0e0000C0effff 70000C77fff sa1801111xxx 64/32 0f0000C0fffff 78000C7ffff sa1910000xxx 64/32 100000C10ffff 80000C87fff sa2010001xxx 64/32 110000C11ffff 88000C8ffff sa2110010xxx 64/32 120000C12ffff 90000C97fff sa2210011xxx 64/32 130000C13ffff 98000C9ffff sa2310100xxx 64/32 140000C14ffff a0000Ca7fff sa2410101xxx 64/32 150000C15ffff a8000Caffff sa2510110xxx 64/32 160000C16ffff b0000Cb7fff sa2610111xxx 64/32 170000C17ffff b8000Cbffff sa2711000xxx 64/32 180000C18ffff c0000Cc7fff sa2811001xxx 64/32 190000C19ffff c8000Ccffff sa2911010xxx 64/32 1a0000C1affff d0000Cd7fff sa3011011xxx 64/32 1b0000C1bffff d8000Cdffff sa3111100xxx 64/32 1c0000C1cffff e0000Ce7fff sa3211101xxx 64/32 1d0000C1dffff e8000Ceffff sa3311110xxx 64/32 1e0000C1effff f0000Cf7fff sa3411111xxx 64/32 1f0000C1fffff f8000Cfffff
preliminary am29lv160b 13 autoselect mode the autoselect mode provides manufacturer and de- vice identification, and sector protection verification, through identifier codes output on dq7Cdq0. this mode is primarily intended for programming equipment to automatically match a device to be programmed with its corresponding programming algorithm. however, the autoselect codes can also be accessed in-system through the command register. when using programming equipment, the autoselect mode requires v id (11.5 v to 12.5 v) on address pin a9. address pins a6, a1, and a0 must be as shown in table 4. in addition, when verifying sector protection, the sector address must appear on the appropriate highest order address bits (see tables 2 and 3). table 4 shows the remaining address bits that are dont care. when all necessary bits have been set as required, the programming equipment may then read the corre- sponding identifier code on dq7-dq0. to access the autoselect codes in-system, the host system can issue the autoselect command via the command register, as shown in table 9. this method does not require v id . see command definitions for details on using the autoselect mode. table 4. am29lv160b autoselect codes (high voltage method) l = logic low = v il , h = logic high = v ih , sa = sector address, x = dont care. note: the autoselect codes may also be accessed in-system via command sequences. see table 9. sector protection/unprotection the hardware sector protection feature disables both program and erase operations in any sector. the hard- ware sector unprotection feature re-enables both pro- gram and erase operations in previously protected sectors. the device is shipped with all sectors unprotected. amd offers the option of programming and protecting sectors at its factory prior to shipping the device through amds expressflash? service. contact an amd representative for details. it is possible to determine whether a sector is protected or unprotected. see autoselect mode for details. sector protection/unprotection can be implemented via two methods. the primary method requires v id on the reset# pin only, and can be implemented either in-system or via programming equipment. figure 1 shows the algo- rithms and figure 23 shows the timing diagram. this method uses standard microprocessor bus cycle tim- ing. for sector unprotect, all unprotected sectors must first be protected prior to the first sector unprotect write cycle. the alternate method intended only for programming equipment requires v id on address pin a9 and oe#. this method is compatible with programmer routines written for earlier 3.0 volt-only amd flash devices. de- tails on this method are provided in a supplement, pub- lication number 21468. contact an amd representative to request a copy. temporary sector unprotect this feature allows temporary unprotection of previ- ously protected sectors to change data in-system. the sector unprotect mode is activated by setting the re- set# pin to v id . during this mode, formerly protected sectors can be programmed or erased by selecting the sector addresses. once v id is removed from the re- set# pin, all the previously protected sectors are protected again. figure 2 shows the algorithm, and figure 22 shows the timing diagrams, for this feature. description mode ce# oe# we# a19 to a12 a11 to a10 a9 a8 to a7 a6 a5 to a2 a1 a0 dq8 to dq15 dq7 to dq0 manufacturer id : amd l l h x x v id xlxll x 01h device id: am29lv160b (top boot block) word l l h xxv id xlxlh 22h c4h byte l l h x c4h device id: am29lv160b (bottom boot block) word l l h xxv id xlxlh 22h 49h byte l l h x 49h sector protection verification l l h sa x v id xlxhl x 01h (protected) x 00h (unprotected)
preliminary 14 am29lv160b figure 1. in-system sector protect/unprotect algorithms sector protect: write 60h to sector address with a6 = 0, a1 = 1, a0 = 0 set up sector address wait 150 s verify sector protect: write 40h to sector address with a6 = 0, a1 = 1, a0 = 0 read from sector address with a6 = 0, a1 = 1, a0 = 0 start plscnt = 1 reset# = v id wait 1 m s first write cycle = 60h? data = 01h? remove v id from reset# write reset command sector protect complete yes yes no plscnt = 25? yes device failed increment plscnt temporary sector unprotect mode no sector unprotect: write 60h to sector address with a6 = 1, a1 = 1, a0 = 0 set up first sector address wait 15 ms verify sector unprotect: write 40h to sector address with a6 = 1, a1 = 1, a0 = 0 read from sector address with a6 = 1, a1 = 1, a0 = 0 start plscnt = 1 reset# = v id wait 1 m s data = 00h? last sector verified? remove v id from reset# write reset command sector unprotect complete yes no plscnt = 1000? yes device failed increment plscnt temporary sector unprotect mode no all sectors protected? yes protect all sectors: the indicated portion of the sector protect algorithm must be performed for all unprotected sectors prior to issuing the first sector unprotect address set up next sector address no yes no yes no no yes no sector protect algorithm sector unprotect algorithm first write cycle = 60h? protect another sector? reset plscnt = 1 21358f-5
preliminary am29lv160b 15 figure 2. temporary sector unprotect operation common flash memory interface (cfi) the common flash interface (cfi) specification out- lines device and host system software interrogation handshake, which allows specific vendor-specified software algorithms to be used for entire families of devices. software support can then be device-inde- pendent, jedec id-independent, and forward- and backward-compatible for the specified flash device families. flash vendors can standardize their existing interfaces for long-term compatibility. this device enters the cfi query mode when the system writes the cfi query command, 98h, to address 55h in word mode (or address aah in byte mode), any time the device is ready to read array data. the system can read cfi information at the addresses given in tables 5C8. in word mode, the upper address bits (a7Cmsb) must be all zeros. to terminate reading cfi data, the system must write the reset command. the system can also write the cfi query command when the device is in the autoselect mode. the device enters the cfi query mode, and the system can read cfi data at the addresses given in tables 5C8. the system must write the reset command to return the device to the autoselect mode. for further information, please refer to the cfi specifi- cation and cfi publication 100, available via the world wide web at http://www.amd.com/products/nvd/over- view/cfi.html. alternatively, contact an amd represent- ative for copies of these documents. start perform erase or program operations reset# = v ih temporary sector unprotect completed (note 2) reset# = v id (note 1) notes: 1. all protected sectors unprotected. 2. all previously protected sectors are protected once again. 21358f-6 table 5. cfi query identification string addresses (word mode) addresses (byte mode) data description 10h 11h 12h 20h 22h 24h 0051h 0052h 0059h query unique ascii string qry 13h 14h 26h 28h 0002h 0000h primary oem command set 15h 16h 2ah 2ch 0040h 0000h address for primary extended table 17h 18h 2eh 30h 0000h 0000h alternate oem command set (00h = none exists) 19h 1ah 32h 34h 0000h 0000h address for alternate oem extended table (00h = none exists)
preliminary 16 am29lv160b table 6. system interface string addresses (word mode) addresses (byte mode) data description 1bh 36h 0027h v cc min. (write/erase) d7Cd4: volt, d3Cd0: 100 millivolt 1ch 38h 0036h v cc max. (write/erase) d7Cd4: volt, d3Cd0: 100 millivolt 1dh 3ah 0000h v pp min. voltage (00h = no v pp pin present) 1eh 3ch 0000h v pp max. voltage (00h = no v pp pin present) 1fh 3eh 0004h typical timeout per single byte/word write 2 n s 20h 40h 0000h typical timeout for min. size buffer write 2 n s (00h = not supported) 21h 42h 000ah typical timeout per individual block erase 2 n ms 22h 44h 0000h typical timeout for full chip erase 2 n ms (00h = not supported) 23h 46h 0005h max. timeout for byte/word write 2 n times typical 24h 48h 0000h max. timeout for buffer write 2 n times typical 25h 4ah 0004h max. timeout per individual block erase 2 n times typical 26h 4ch 0000h max. timeout for full chip erase 2 n times typical (00h = not supported) table 7. device geometry definition addresses (word mode) addresses (byte mode) data description 27h 4eh 0015h device size = 2 n byte 28h 29h 50h 52h 0002h 0000h flash device interface description (refer to cfi publication 100) 2ah 2bh 54h 56h 0000h 0000h max. number of byte in multi-byte write = 2 n (00h = not supported) 2ch 58h 0004h number of erase block regions within device 2dh 2eh 2fh 30h 5ah 5ch 5eh 60h 0000h 0000h 0040h 0000h erase block region 1 information (refer to the cfi specification or cfi publication 100) 31h 32h 33h 34h 62h 64h 66h 68h 0001h 0000h 0020h 0000h erase block region 2 information 35h 36h 37h 38h 6ah 6ch 6eh 70h 0000h 0000h 0080h 0000h erase block region 3 information 39h 3ah 3bh 3ch 72h 74h 76h 78h 001eh 0000h 0000h 0001h erase block region 4 information
preliminary am29lv160b 17 hardware data protection the command sequence requirement of unlock cycles for programming or erasing provides data protection against inadvertent writes (refer to table 9 for com- mand definitions). in addition, the following hardware data protection measures prevent accidental erasure or programming, which might otherwise be caused by spurious system level signals during v cc power-up and power-down transitions, or from system noise. low v cc write inhibit when v cc is less than v lko , the device does not ac- cept any write cycles. this protects data during v cc power-up and power-down. the command register and all internal program/erase circuits are disabled, and the device resets. subsequent writes are ignored until v cc is greater than v lko . the system must provide the proper signals to the control pins to prevent uninten- tional writes when v cc is greater than v lko . write pulse glitch protection noise pulses of less than 5 ns (typical) on oe#, ce# or we# do not initiate a write cycle. logical inhibit write cycles are inhibited by holding any one of oe# = v il , ce# = v ih or we# = v ih . to initiate a write cycle, ce# and we# must be a logical zero while oe# is a logical one. power-up write inhibit if we# = ce# = v il and oe# = v ih during power up, the device does not accept commands on the rising edge of we#. the internal state machine is automatically reset to reading array data on power-up. table 8. primary vendor-specific extended query addresses (word mode) addresses (byte mode) data description 40h 41h 42h 80h 82h 84h 0050h 0052h 0049h query-unique ascii string pri 43h 86h 0031h major version number, ascii 44h 88h 0030h minor version number, ascii 45h 8ah 0000h address sensitive unlock 0 = required, 1 = not required 46h 8ch 0002h erase suspend 0 = not supported, 1 = to read only, 2 = to read & write 47h 8eh 0001h sector protect 0 = not supported, x = number of sectors in per group 48h 90h 0001h sector temporary unprotect 00 = not supported, 01 = supported 49h 92h 0004h sector protect/unprotect scheme 01 = 29f040 mode, 02 = 29f016 mode, 03 = 29f400 mode, 04 = 29lv800a mode 4ah 94h 0000h simultaneous operation 00 = not supported, 01 = supported 4bh 96h 0000h burst mode type 00 = not supported, 01 = supported 4ch 98h 0000h page mode type 00 = not supported, 01 = 4 word page, 02 = 8 word page
preliminary 18 am29lv160b command definitions writing specific address and data commands or se- quences into the command register initiates device op- erations. table 9 defines the valid register command sequences. writing incorrect address and data val- ues or writing them in the improper sequence resets the device to reading array data. all addresses are latched on the falling edge of we# or ce#, whichever happens later. all data is latched on the rising edge of we# or ce#, whichever happens first. refer to the appropriate timing diagrams in the ac characteristics section. reading array data the device is automatically set to reading array data after device power-up. no commands are required to retrieve data. the device is also ready to read array data after completing an embedded program or em- bedded erase algorithm. after the device accepts an erase suspend com- mand, the device enters the erase suspend mode. the system can read array data using the standard read timings, except that if it reads at an address within erase-suspended sectors, the device outputs status data. after completing a programming opera- tion in the erase suspend mode, the system may once again read array data with the same exception. see erase suspend/erase resume commands for more information on this mode. the system must issue the reset command to re-ena- ble the device for reading array data if dq5 goes high, or while in the autoselect mode. see the reset com- mand section, next. see also requirements for reading array data in the device bus operations section for more information. the read operations table provides the read parame- ters, and figure 13 shows the timing diagram. reset command writing the reset command to the device resets the de- vice to reading array data. address bits are dont care for this command. the reset command may be written between the se- quence cycles in an erase command sequence before erasing begins. this resets the device to reading array data. once erasure begins, however, the device ig- nores reset commands until the operation is complete. the reset command may be written between the se- quence cycles in a program command sequence be- fore programming begins. this resets the device to reading array data (also applies to programming in erase suspend mode). once programming begins, however, the device ignores reset commands until the operation is complete. the reset command may be written between the se- quence cycles in an autoselect command sequence. once in the autoselect mode, the reset command must be written to return to reading array data (also applies to autoselect during erase suspend). if dq5 goes high during a program or erase operation, writing the reset command returns the device to read- ing array data (also applies during erase suspend). see ac characteristics for parameters, and to figure 14 for the timing diagram. autoselect command sequence the autoselect command sequence allows the host system to access the manufacturer and devices codes, and determine whether or not a sector is protected. table 9 shows the address and data requirements. this method is an alternative to that shown in table 4, which is intended for prom programmers and requires v id on address bit a9. the autoselect command sequence is initiated by writ- ing two unlock cycles, followed by the autoselect com- mand. the device then enters the autoselect mode, and the system may read at any address any number of times, without initiating another command sequence. a read cycle at address xx00h retrieves the manufac- turer code. a read cycle at address xx01h returns the device code. a read cycle containing a sector address (sa) and the address 02h in word mode (or 04h in byte mode) returns 01h if that sector is protected, or 00h if it is unprotected. refer to tables 2 and 3 for valid sector addresses. the system must write the reset command to exit the autoselect mode and return to reading array data. word/byte program command sequence the system may program the device by word or byte, depending on the state of the byte# pin. program- ming is a four-bus-cycle operation. the program com- mand sequence is initiated by writing two unlock write cycles, followed by the program set-up command. the program address and data are written next, which in turn initiate the embedded program algorithm. the system is not required to provide further controls or timings. the device automatically generates the pro- gram pulses and verifies the programmed cell margin. table 9 shows the address and data requirements for the byte program command sequence. when the embedded program algorithm is complete, the device then returns to reading array data and ad- dresses are no longer latched. the system can deter- mine the status of the program operation by using dq7, dq6, or ry/by#. see write operation status for information on these status bits.
preliminary am29lv160b 19 any commands written to the device during the em- bedded program algorithm are ignored. note that a hardware reset immediately terminates the program- ming operation. the byte program command se- quence should be reinitiated once the device has reset to reading array data, to ensure data integrity. programming is allowed in any sequence and across sector boundaries. a bit cannot be programmed from a 0 back to a 1. attempting to do so may halt the operation and set dq5 to 1, or cause the data# polling algorithm to indicate the operation was suc- cessful. however, a succeeding read will show that the data is still 0. only erase operations can convert a 0 to a 1. unlock bypass command sequence the unlock bypass feature allows the system to pro- gram bytes or words to the device faster than using the standard program command sequence. the unlock by- pass command sequence is initiated by first writing two unlock cycles. this is followed by a third write cycle containing the unlock bypass command, 20h. the de- vice then enters the unlock bypass mode. a two-cycle unlock bypass program command sequence is all that is required to program in this mode. the first cycle in this sequence contains the unlock bypass program command, a0h; the second cycle contains the program address and data. additional data is programmed in the same manner. this mode dispenses with the initial two unlock cycles required in the standard program command sequence, resulting in faster total program- ming time. table 9 shows the requirements for the com- mand sequence. during the unlock bypass mode, only the unlock by- pass program and unlock bypass reset commands are valid. to exit the unlock bypass mode, the system must issue the two-cycle unlock bypass reset com- mand sequence. the first cycle must contain the data 90h; the second cycle the data 00h. addresses are dont care for both cycles. the device then returns to reading array data. figure 3 illustrates the algorithm for the program oper- ation. see the erase/program operations table in ac characteristics for parameters, and to figure 17 for timing diagrams. note: see table 9 for program command sequence. figure 3. program operation chip erase command sequence chip erase is a six bus cycle operation. the chip erase command sequence is initiated by writing two unlock cycles, followed by a set-up command. two additional unlock write cycles are then followed by the chip erase command, which in turn invokes the embedded erase algorithm. the device does not require the system to preprogram prior to erase. the embedded erase algo- rithm automatically preprograms and verifies the entire memory for an all zero data pattern prior to electrical erase. the system is not required to provide any con- trols or timings during these operations. table 9 shows the address and data requirements for the chip erase command sequence. any commands written to the chip during the embed- ded erase algorithm are ignored. note that a hardware reset during the chip erase operation immediately ter- minates the operation. the chip erase command se- quence should be reinitiated once the device has returned to reading array data, to ensure data integrity. start write program command sequence data poll from system verify data? no yes last address? no yes programming completed increment address embedded program algorithm in progress 21358f-7
preliminary 20 am29lv160b the system can determine the status of the erase op- eration by using dq7, dq6, dq2, or ry/by#. see write operation status for information on these sta- tus bits. when the embedded erase algorithm is com- plete, the device returns to reading array data and addresses are no longer latched. figure 4 illustrates the algorithm for the erase opera- tion. see the erase/program operations tables in ac characteristics for parameters, and to figure 18 for timing diagrams. sector erase command sequence sector erase is a six bus cycle operation. the sector erase command sequence is initiated by writing two unlock cycles, followed by a set-up command. two ad- ditional unlock write cycles are then followed by the ad- dress of the sector to be erased, and the sector erase command. table 9 shows the address and data re- quirements for the sector erase command sequence. the device does not require the system to preprogram the memory prior to erase. the embedded erase algo- rithm automatically programs and verifies the sector for an all zero data pattern prior to electrical erase. the system is not required to provide any controls or tim- ings during these operations. after the command sequence is written, a sector erase time-out of 50 s begins. during the time-out period, additional sector addresses and sector erase com- mands may be written. loading the sector erase buffer may be done in any sequence, and the number of sec- tors may be from one sector to all sectors. the time be- tween these additional cycles must be less than 50 s, otherwise the last address and command might not be accepted, and erasure may begin. it is recommended that processor interrupts be disabled during this time to ensure all commands are accepted. the interrupts can be re-enabled after the last sector erase command is written. if the time between additional sector erase commands can be assumed to be less than 50 s, the system need not monitor dq3. any command other than sector erase or erase suspend during the time-out period resets the device to reading array data. the system must rewrite the command sequence and any additional sector addresses and commands. the system can monitor dq3 to determine if the sector erase timer has timed out. (see the dq3: sector erase timer section.) the time-out begins from the rising edge of the final we# pulse in the command sequence. once the sector erase operation has begun, only the erase suspend command is valid. all other commands are ignored. note that a hardware reset during the sector erase operation immediately terminates the op- eration. the sector erase command sequence should be reinitiated once the device has returned to reading array data, to ensure data integrity. when the embedded erase algorithm is complete, the device returns to reading array data and addresses are no longer latched. the system can determine the sta- tus of the erase operation by using dq7, dq6, dq2, or ry/by#. (refer to write operation status for informa- tion on these status bits.) figure 4 illustrates the algorithm for the erase opera- tion. refer to the erase/program operations tables in the ac characteristics section for parameters, and to figure 18 for timing diagrams. erase suspend/erase resume commands the erase suspend command allows the system to in- terrupt a sector erase operation and then read data from, or program data to, any sector not selected for erasure. this command is valid only during the sector erase operation, including the 50 s time-out period during the sector erase command sequence. the erase suspend command is ignored if written during the chip erase operation or embedded program algo- rithm. writing the erase suspend command during the sector erase time-out immediately terminates the time-out period and suspends the erase operation. ad- dresses are dont-cares when writing the erase sus- pend command. when the erase suspend command is written during a sector erase operation, the device requires a maximum of 20 s to suspend the erase operation. however, when the erase suspend command is written during the sector erase time-out, the device immediately ter- minates the time-out period and suspends the erase operation. after the erase operation has been suspended, the system can read array data from or program data to any sector not selected for erasure. (the device erase suspends all sectors selected for erasure.) normal read and write timings and command definitions apply. reading at any address within erase-suspended sec- tors produces status data on dq7Cdq0. the system can use dq7, or dq6 and dq2 together, to determine if a sector is actively erasing or is erase-suspended. see write operation status for information on these status bits. after an erase-suspended program operation is com- plete, the system can once again read array data within non-suspended sectors. the system can determine the status of the program operation using the dq7 or dq6 status bits, just as in the standard program operation. see write operation status for more information. the system may also write the autoselect command sequence when the device is in the erase suspend mode. the device allows reading autoselect codes even at addresses within erasing sectors, since the codes are not stored in the memory array. when the device exits the autoselect mode, the device reverts to the erase suspend mode, and is ready for another
preliminary am29lv160b 21 valid operation. see autoselect command sequence for more information. the system must write the erase resume command (address bits are dont care) to exit the erase suspend mode and continue the sector erase operation. further writes of the resume command are ignored. another erase suspend command can be written after the de- vice has resumed erasing. notes: 1. see table 9 for erase command sequence. 2. see dq3: sector erase timer for more information. figure 4. erase operation start write erase command sequence data poll from system data = ffh? no yes erasure completed embedded erase algorithm in progress 21358f-8
preliminary 22 am29lv160b table 9. am29lv160b command definitions legend: x = dont care ra = address of the memory location to be read. rd = data read from location ra during read operation. pa = address of the memory location to be programmed. addresses latch on the falling edge of the we# or ce# pulse, whichever happens later. pd = data to be programmed at location pa. data latches on the rising edge of we# or ce# pulse, whichever happens first. sa = address of the sector to be verified (in autoselect mode) or erased. address bits a19Ca12 uniquely select any sector. notes: 1. see table 1 for description of bus operations. 2. all values are in hexadecimal. 3. except for the read cycle and the fourth cycle of the autoselect command sequence, all bus cycles are write cycles. 4. data bits dq15Cdq8 are dont cares for unlock and command cycles. 5. address bits a19Ca11 are dont cares for unlock and command cycles, unless sa or pa required. 6. no unlock or command cycles required when reading array data. 7. the reset command is required to return to reading array data when device is in the autoselect mode, or if dq5 goes high (while the device is providing status data). 8. the fourth cycle of the autoselect command sequence is a read cycle. 9. the data is 00h for an unprotected sector and 01h for a protected sector. see autoselect command sequence for more information. 10. command is valid when device is ready to read array data or when device is in autoselect mode. 11. the unlock bypass command is required prior to the unlock bypass program command. 12. the unlock bypass reset command is required to return to reading array data when the device is in the unlock bypass mode. 13. the system may read and program in non-erasing sectors, or enter the autoselect mode, when in the erase suspend mode. the erase suspend command is valid only during a sector erase operation. 14. the erase resume command is valid only during the erase suspend mode. command sequence (note 1) bus cycles (notes 2C5) first second third fourth fifth sixth addr data addr data addr data addr data addr data addr data read (note 6) 1 ra rd reset (note 7) 1 xxx f0 manufacturer id word 4 555 aa 2aa 55 555 90 x00 01 byte aaa 555 aaa device id, top boot block word 4 555 aa 2aa 55 555 90 x01 22c4 byte aaa 555 aaa x02 c4 device id, bottom boot block word 4 555 aa 2aa 55 555 90 x01 2249 byte aaa 555 aaa x02 49 sector protect verify (note 9) word 4 555 aa 2aa 55 555 90 (sa) x02 xx00 xx01 byte aaa 555 aaa (sa) x04 00 01 cfi query (note 10) word 1 55 98 byte aa program word 4 555 aa 2aa 55 555 a0 pa pd byte aaa 555 aaa unlock bypass word 3 555 aa 2aa 55 555 20 byte aaa 555 aaa unlock bypass program (note 11) 2 xxx a0 pa pd unlock bypass reset (note 12) 2 xxx 90 xxx 00 chip erase word 6 555 aa 2aa 55 555 80 555 aa 2aa 55 555 10 byte aaa 555 aaa aaa 555 2aa sector erase word 6 555 aa 2aa 55 555 80 555 aa 2aa 55 sa 30 byte aaa 555 aaa aaa 555 erase suspend (note 13) 1 xxx b0 erase resume (note 14) 1 xxx 30 cycles autoselect (note 8)
preliminary am29lv160b 23 write operation status the device provides several bits to determine the sta- tus of a write operation: dq2, dq3, dq5, dq6, dq7, and ry/by#. table 10 and the following subsections describe the functions of these bits. dq7, ry/by#, and dq6 each offer a method for determining whether a program or erase operation is complete or in progress. these three bits are discussed first. dq7: data# polling the data# polling bit, dq7, indicates to the host system whether an embedded algorithm is in progress or com- pleted, or whether the device is in erase suspend. data# polling is valid after the rising edge of the final we# pulse in the program or erase command se- quence. during the embedded program algorithm, the device outputs on dq7 the complement of the datum pro- grammed to dq7. this dq7 status also applies to pro- gramming during erase suspend. when the embedded program algorithm is complete, the device outputs the datum programmed to dq7. the system must provide the program address to read valid status information on dq7. if a program address falls within a protected sector, data# polling on dq7 is active for ap- proximately 1 s, then the device returns to reading array data. during the embedded erase algorithm, data# polling produces a 0 on dq7. when the embedded erase al- gorithm is complete, or if the device enters the erase suspend mode, data# polling produces a 1 on dq7. this is analogous to the complement/true datum output described for the embedded program algorithm: the erase function changes all the bits in a sector to 1; prior to this, the device outputs the complement, or 0. the system must provide an address within any of the sectors selected for erasure to read valid status in- formation on dq7. after an erase command sequence is written, if all sec- tors selected for erasing are protected, data# polling on dq7 is active for approximately 100 s, then the de- vice returns to reading array data. if not all selected sectors are protected, the embedded erase algorithm erases the unprotected sectors, and ignores the se- lected sectors that are protected. when the system detects dq7 has changed from the complement to true data, it can read valid data at dq7C dq0 on the following read cycles. this is because dq7 may change asynchronously with dq0Cdq6 while output enable (oe#) is asserted low. figure 19, data# polling timings (during embedded algorithms), in the ac characteristics section illustrates this. table 10 shows the outputs for data# polling on dq7. figure 5 shows the data# polling algorithm. dq7 = data? yes no no dq5 = 1? no yes yes fail pass read dq7Cdq0 addr = va read dq7Cdq0 addr = va dq7 = data? start notes: 1. va = valid address for programming. during a sector erase operation, a valid address is an address within any sector selected for erasure. during chip erase, a valid address is any non-protected sector address. 2. dq7 should be rechecked even if dq5 = 1 because dq7 may change simultaneously with dq5. 21358f-9 figure 5. data# polling algorithm
preliminary 24 am29lv160b ry/by#: ready/busy# the ry/by# is a dedicated, open-drain output pin that indicates whether an embedded algorithm is in progress or complete. the ry/by# status is valid after the rising edge of the final we# pulse in the command sequence. since ry/by# is an open-drain output, sev- eral ry/by# pins can be tied together in parallel with a pull-up resistor to v cc . (the ry/by# pin is not availa- ble on the 44-pin so package.) if the output is low (busy), the device is actively erasing or programming. (this includes programming in the erase suspend mode.) if the output is high (ready), the device is ready to read array data (including during the erase suspend mode), or is in the standby mode. table 10 shows the outputs for ry/by#. figures 13, 14, 17 and 18 shows ry/by# for read, reset, program, and erase operations, respectively. dq6: toggle bit i toggle bit i on dq6 indicates whether an embedded program or erase algorithm is in progress or complete, or whether the device has entered the erase suspend mode. toggle bit i may be read at any address, and is valid after the rising edge of the final we# pulse in the command sequence (prior to the program or erase op- eration), and during the sector erase time-out. during an embedded program or erase algorithm op- eration, successive read cycles to any address cause dq6 to toggle. (the system may use either oe# or ce# to control the read cycles.) when the operation is complete, dq6 stops toggling. after an erase command sequence is written, if all sec- tors selected for erasing are protected, dq6 toggles for approximately 100 s, then returns to reading array data. if not all selected sectors are protected, the em- bedded erase algorithm erases the unprotected sec- tors, and ignores the selected sectors that are protected. the system can use dq6 and dq2 together to deter- mine whether a sector is actively erasing or is erase- suspended. when the device is actively erasing (that is, the embedded erase algorithm is in progress), dq6 toggles. when the device enters the erase suspend mode, dq6 stops toggling. however, the system must also use dq2 to determine which sectors are erasing or erase-suspended. alternatively, the system can use dq7 (see the subsection on dq7: data# polling). if a program address falls within a protected sector, dq6 toggles for approximately 1 s after the program command sequence is written, then returns to reading array data. dq6 also toggles during the erase-suspend-program mode, and stops toggling once the embedded pro- gram algorithm is complete. table 10 shows the outputs for toggle bit i on dq6. fig- ure 6 shows the toggle bit algorithm in flowchart form, and the section reading toggle bits dq6/dq2 ex- plains the algorithm. figure 20 in the ac characteris- tics section shows the toggle bit timing diagrams. figure 21 shows the differences between dq2 and dq6 in graphical form. see also the subsection on dq2: toggle bit ii. dq2: toggle bit ii the toggle bit ii on dq2, when used with dq6, indi- cates whether a particular sector is actively erasing (that is, the embedded erase algorithm is in progress), or whether that sector is erase-suspended. toggle bit ii is valid after the rising edge of the final we# pulse in the command sequence. dq2 toggles when the system reads at addresses within those sectors that have been selected for eras- ure. (the system may use either oe# or ce# to control the read cycles.) but dq2 cannot distinguish whether the sector is actively erasing or is erase-suspended. dq6, by comparison, indicates whether the device is actively erasing, or is in erase suspend, but cannot distinguish which sectors are selected for erasure. thus, both status bits are required for sector and mode information. refer to table 10 to compare outputs for dq2 and dq6. figure 6 shows the toggle bit algorithm in flowchart form, and the section reading toggle bits dq6/dq2 explains the algorithm. see also the dq6: toggle bit i subsection. figure 20 shows the toggle bit timing dia- gram. figure 21 shows the differences between dq2 and dq6 in graphical form. reading toggle bits dq6/dq2 refer to figure 6 for the following discussion. when- ever the system initially begins reading toggle bit sta- tus, it must read dq7Cdq0 at least twice in a row to determine whether a toggle bit is toggling. typically, the system would note and store the value of the tog- gle bit after the first read. after the second read, the system would compare the new value of the toggle bit with the first. if the toggle bit is not toggling, the device has completed the program or erase operation. the system can read array data on dq7Cdq0 on the fol- lowing read cycle. however, if after the initial two read cycles, the system determines that the toggle bit is still toggling, the sys- tem also should note whether the value of dq5 is high (see the section on dq5). if it is, the system should then determine again whether the toggle bit is toggling, since the toggle bit may have stopped toggling just as dq5 went high. if the toggle bit is no longer toggling, the device has successfully completed the program or erase operation. if it is still toggling, the device did not complete the operation successfully, and the system
preliminary am29lv160b 25 must write the reset command to return to reading array data. the remaining scenario is that the system initially de- termines that the toggle bit is toggling and dq5 has not gone high. the system may continue to monitor the toggle bit and dq5 through successive read cycles, de- termining the status as described in the previous para- graph. alternatively, it may choose to perform other system tasks. in this case, the system must start at the beginning of the algorithm when it returns to determine the status of the operation (top of figure 6). dq5: exceeded timing limits dq5 indicates whether the program or erase time has exceeded a specified internal pulse count limit. under these conditions dq5 produces a 1. this is a failure condition that indicates the program or erase cycle was not successfully completed. the dq5 failure condition may appear if the system tries to program a 1 to a location that is previously programmed to 0. only an erase operation can change a 0 back to a 1. under this condition, the device halts the operation, and when the operation has exceeded the timing limits, dq5 produces a 1. under both these conditions, the system must issue the reset command to return the device to reading array data. dq3: sector erase timer after writing a sector erase command sequence, the system may read dq3 to determine whether or not an erase operation has begun. (the sector erase timer does not apply to the chip erase command.) if additional sectors are selected for erasure, the entire time-out also applies after each additional sector erase command. when the time-out is complete, dq3 switches from 0 to 1. the system may ignore dq3 if the system can guarantee that the time between additional sector erase commands will always be less than 50 m s. see also the sector erase command sequence section. after the sector erase command sequence is written, the system should read the status on dq7 (data# poll- ing) or dq6 (toggle bit i) to ensure the device has ac- cepted the command sequence, and then read dq3. if dq3 is 1, the internally controlled erase cycle has be- gun; all further commands (other than erase suspend) are ignored until the erase operation is complete. if dq3 is 0, the device will accept additional sector erase commands. to ensure the command has been accepted, the system software should check the status of dq3 prior to and following each subsequent sector erase command. if dq3 is high on the second status check, the last command might not have been ac- cepted. table 10 shows the outputs for dq3. start no yes yes dq5 = 1? no yes toggle bit = toggle? no program/erase operation not complete, write reset command program/erase operation complete read dq7Cdq0 toggle bit = toggle? read dq7Cdq0 twice read dq7Cdq0 notes: 1. read toggle bit twice to determine whether or not it is toggling. see text. 2. recheck toggle bit because it may stop toggling as dq5 changes to 1. see text. 21358f-10 figure 6. toggle bit algorithm (note 1) (notes 1, 2)
preliminary 26 am29lv160b table 10. write operation status notes: 1. dq5 switches to 1 when an embedded program or embedded erase operation has exceeded the maximum timing limits. see dq5: exceeded timing limits for more information. 2. dq7 and dq2 require a valid address when reading status information. refer to the appropriate subsection for further details. operation dq7 (note 2) dq6 dq5 (note 1) dq3 dq2 (note 2) ry/by# standard mode embedded program algorithm dq7# toggle 0 n/a no toggle 0 embedded erase algorithm 0 toggle 0 1 toggle 0 erase suspend mode reading within erase suspended sector 1 no toggle 0 n/a toggle 1 reading within non-erase suspended sector data data data data data 1 erase-suspend-program dq7# toggle 0 n/a n/a 0
preliminary am29lv160b 27 absolute maximum ratings storage temperature plastic packages . . . . . . . . . . . . . . . C65 c to +150 c ambient temperature with power applied. . . . . . . . . . . . . . C65 c to +125 c voltage with respect to ground v cc (note 1) . . . . . . . . . . . . . . . . . . C0.5 v to +4.0 v a9 , oe# , and reset# (note 2) . . C0.5 v to +12.5 v all other pins (note 1). . . . . . . C0.5 v to v cc +0.5 v output short circuit current (note 3) . . . . . . 200 ma notes: 1. minimum dc voltage on input or i/o pins is C0.5 v. during voltage transitions, input or i/o pins may undershoot v ss to C2.0 v for periods of up to 20 ns. see figure 7. maximum dc voltage on input or i/o pins is v cc +0.5 v. during voltage transitions, input or i/o pins may overshoot to v cc +2.0 v for periods up to 20 ns. see figure 8. 2. minimum dc input voltage on pins a9, oe#, and reset# is -0.5 v. during voltage transitions, a9, oe#, and reset# may undershoot v ss to C2.0 v for periods of up to 20 ns. see figure 7. maximum dc input voltage on pin a9 is +12.5 v which may overshoot to 14.0 v for periods up to 20 ns. 3. no more than one output may be shorted to ground at a time. duration of the short circuit should not be greater than one second. stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating only; functional operation of the device at these or any other conditions above those indicated in the operational sections of this data sheet is not implied. exposure of the device to absolute maximum rating conditions for extended periods may affect device reliability. figure 7. maximum negative overshoot waveform figure 8. maximum positive overshoot waveform operating ranges commercial (c) devices ambient temperature (t a ) . . . . . . . . . . . 0c to +70c industrial (i) devices ambient temperature (t a ) . . . . . . . . . C40c to +85c extended (e) devices ambient temperature (t a ) . . . . . . . . C55c to +125c v cc supply voltages v cc for regulated voltage range. . . . . . . 3.0 v to 3.6 v v cc for full voltage range . . . . . . . . . . . . 2.7 v to 3.6 v operating ranges define those limits between which the func- tionality of the device is guaranteed. 20 ns 20 ns +0.8 v C0.5 v 20 ns C2.0 v 21358f-11 20 ns 20 ns v cc +2.0 v v cc +0.5 v 20 ns 2.0 v 21358f-1
preliminary 28 am29lv160b dc characteristics cmos compatible notes: 1. the i cc current listed is typically less than 2 ma/mhz, with oe# at v ih . typical v cc is 3.0 v. 2. i cc active while embedded erase or embedded program is in progress. 3. automatic sleep mode enables the low power mode when addresses remain stable for t acc + 30 ns. typical sleep mode current is 200 na. 4. not 100% tested. parameter description test conditions min typ max unit i li input load current v in = v ss to v cc , v cc = v cc max 1.0 a i lit a9 input load current v cc = v cc max ; a9 = 12.5 v 35 a i lo output leakage current v out = v ss to v cc , v cc = v cc max 1.0 a i cc1 v cc active read current (note 1) ce# = v il, oe# = v ih, byte mode 5 mhz 9 16 ma 1 mhz 2 4 ce# = v il, oe# = v ih, word mode 5 mhz 9 16 1 mhz 2 4 i cc2 v cc active write current (notes 2 and 4) ce# = v il, oe# = v ih 20 30 ma i cc3 v cc standby current v cc = v cc max ; ce#, reset# = v cc 0.3 v 0.2 5 a i cc4 v cc standby current during reset v cc = v cc max ; reset# = v ss 0.3 v 0.2 5 a i cc5 automatic sleep mode (note 3) v ih = v cc 0.3 v; v il = v ss 0.3 v 0.2 5 a v il input low voltage C0.5 0.8 v v ih input high voltage 0.7 x v cc v cc + 0.3 v v id voltage for autoselect and temporary sector unprotect v cc = 3.3 v 11.5 12.5 v v ol output low voltage i ol = 4.0 ma, v cc = v cc min 0.45 v v oh1 output high voltage i oh = -2.0 ma, v cc = v cc min 0.85 x v cc v v oh2 i oh = -100 a, v cc = v cc min v cc C0.4 v lko low v cc lock-out voltage (note 4) 2.3 2.5 v
preliminary am29lv160b 29 dc characteristics (continued) zero power flash note: addresses are switching at 1 mhz 21358f-13 figure 9. i cc1 current vs. time (showing active and automatic sleep currents) 25 20 15 10 5 0 0 500 1000 1500 2000 2500 3000 3500 4000 supply current in ma time in ns 10 8 2 0 12345 frequency in mhz supply current in ma note: t = 25 c 21358f-14 figure 10. typical i cc1 vs. frequency 2.7 v 3.6 v 4 6
preliminary 30 am29lv160b test conditions table 11. test specifications key to switching waveforms 2.7 k w c l 6.2 k w 3.3 v device under te s t 21358f-15 figure 11. test setup note: diodes are in3064 or equivalent test condition 80r 90, 120 unit output load 1 ttl gate output load capacitance, c l (including jig capacitance) 30 100 pf input rise and fall times 5 ns input pulse levels 0.0C3.0 v input timing measurement reference levels 1.5 v output timing measurement reference levels 1.5 v ks000010-pal waveform inputs outputs steady changing from h to l changing from l to h dont care, any change permitted changing, state unknown does not apply center line is high impedance state (high z) 3.0 v 0.0 v 1.5 v 1.5 v output measurement level input 21358f-16 figure 12. input waveforms and measurement levels
preliminary am29lv160b 31 ac characteristics read operations notes: 1. not 100% tested. 2. see figure 11 and table 11 for test specifications. parameter description speed option jedec std test setup 80r 90 120 unit t avav t rc read cycle time (note 1) min 80 90 120 ns t avqv t acc address to output delay ce# = v il oe# = v il max 80 90 120 ns t elqv t ce chip enable to output delay oe# = v il max 80 90 120 ns t glqv t oe output enable to output delay max 30 35 50 ns t ehqz t df chip enable to output high z (note 1) max 25 30 30 ns t ghqz t df output enable to output high z (note 1) max 25 30 30 ns t oeh output enable hold time (note 1) read min 0 ns toggle and data# polling min 10 ns t axqx t oh output hold time from addresses, ce# or oe#, whichever occurs first (note 1) min 0 ns t ce outputs we# addresses ce# oe# high z output valid high z addresses stable t rc t acc t oeh t oe 0 v ry/by# reset# t df t oh 21358f-17 figure 13. read operations timings
preliminary 32 am29lv160b ac characteristics hardware reset (reset#) note: not 100% tested. parameter description speed option jedec std test setup 80r 90 120 unit t ready reset# pin low (during embedded algorithms) to read or write (see note) max 20 s t ready reset# pin low (not during embedded algorithms) to read or write (see note) max 500 ns t rp reset# pulse width min 500 ns t rh reset# high time before read (see note) min 50 ns t rpd reset# low to standby mode min 20 s t rb ry/by# recovery time min 0 ns reset# ry/by# ry/by# t rp t ready reset timings not during embedded algorithms t ready ce#, oe# t rh ce#, oe# reset timings during embedded algorithms reset# t rp t rb 21358f-18 figure 14. reset# timings
preliminary am29lv160b 33 ac characteristics word/byte configuration (byte#) parameter 80r 90 120 jedec std description unit t elfl/ t elfh ce# to byte# switching low or high max 5 ns t flqz byte# switching low to output high z max 25 30 30 ns t fhqv byte# switching high to output active min 80 90 120 ns dq15 output data output (dq0Cdq7) ce# oe# byte# t elfl dq0Cdq14 data output (dq0Cdq14) dq15/a-1 address input t flqz byte# switching from word to byte mode dq15 output data output (dq0Cdq7) byte# t elfh dq0Cdq14 data output (dq0Cdq14) dq15/a-1 address input t fhqv byte# switching from byte to word mode 21358f-19 figure 15. byte# timings for read operations note: refer to the erase/program operations table for t as and t ah specifications. 21358f-20 figure 16. byte# timings for write operations ce# we# byte# the falling edge of the last we# signal t hold (t ah ) t set (t as )
preliminary 34 am29lv160b ac characteristics erase/program operations notes: 1. not 100% tested. 2. see the erase and programming performance section for more information. parameter 80r 90 120 jedec std description unit t avav t wc write cycle time (note 1) min 80 90 120 ns t avwl t as address setup time min 0 ns t wlax t ah address hold time min 45 45 50 ns t dvwh t ds data setup time min 35 45 50 ns t whdx t dh data hold time min 0 ns t oes output enable setup time min 0 ns t ghwl t ghwl read recovery time before write (oe# high to we# low) min 0 ns t elwl t cs ce# setup time min 0 ns t wheh t ch ce# hold time min 0 ns t wlwh t wp write pulse width min 35 35 50 ns t whwl t wph write pulse width high min 30 ns t whwh1 t whwh1 programming operation (note 2) byte typ 9 s word typ 11 t whwh2 t whwh2 sector erase operation (note 2) typ 0.7 sec t vcs v cc setup time (note 1) min 50 s t rb recovery time from ry/by# min 0 ns t busy program/erase valid to ry/by# delay min 90 ns
preliminary am29lv160b 35 ac characteristics notes: 1. pa = program address, pd = program data, d out is the true data at the program address. 2. illustration shows device in word mode. figure 17. program operation timings oe# we# ce# v cc data addresses t ds t ah t dh t wp pd t whwh1 t wc t as t wph t vcs 555h pa pa read status data (last two cycles) a0h t ghwl t cs status d out program command sequence (last two cycles) ry/by# t rb t busy t ch pa 21358f-21
preliminary 36 am29lv160b ac characteristics notes: 1. sa = sector address (for sector erase), va = valid address for reading status data (see write operation status). 2. illustration shows device in word mode. figure 18. chip/sector erase operation timings oe# ce# addresses v cc we# data 2aah sa t ghwl t ah t wp t wc t as t wph 555h for chip erase 10 for chip erase 30h t ds t vcs t cs t dh 55h t ch in progress complete t whwh2 va va erase command sequence (last two cycles) read status data ry/by# t rb t busy 21358f-22
preliminary am29lv160b 37 ac characteristics we# ce# oe# high z t oe high z dq7 dq0Cdq6 ry/by# t busy complement true addresses va t oeh t ce t ch t oh t df va va status data complement status data true valid data valid data t acc t rc note: va = valid address. illustration shows first status cycle after command sequence, last status read cycle, and array data read cycle. 21358f-23 figure 19. data# polling timings (during embedded algorithms) we# ce# oe# high z t oe dq6/dq2 ry/by# t busy addresses va t oeh t ce t ch t oh t df va va t acc t rc valid data valid status valid status (first read) (second read) (stops toggling) valid status va note: va = valid address; not required for dq6. illustration shows first two status cycle after command sequence, last status read cycle, and array data read cycle. 21358f-24 figure 20. toggle bit timings (during embedded algorithms)
preliminary 38 am29lv160b ac characteristics temporary sector unprotect note: not 100% tested. parameter 80r 90 120 jedec std. description unit t vidr v id rise and fall time (see note) min 500 ns t rsp reset# setup time for temporary sector unprotect min 4 s note: the system may use ce# or oe# to toggle dq2 and dq6. dq2 toggles only when read at an address within an erase-suspended sector. 21358f-25 figure 21. dq2 vs. dq6 for erase and erase suspend operations enter erase erase erase enter erase suspend program erase suspend read erase suspend read erase we# dq6 dq2 erase complete erase suspend suspend program resume embedded erasing reset# t vidr 12 v 0 or 3 v ce# we# ry/by# t vidr t rsp program or erase command sequence 21358f-26 figure 22. temporary sector unprotect timing diagram
preliminary am29lv160b 39 ac characteristics sector protect: 100 s sector unprot ect: 10 ms 1 s reset# sa, a6, a1, a0 data ce# we# oe# 60h 60h 40h valid* valid* valid* status sector protect/unprotect verify v id v ih note: for sector protect, a6 = 0, a1 = 1, a0 = 0. for sector unprotect, a6 = 1, a1 = 1, a0 = 0. 21358f-27 figure 23. sector protect/unprotect timing diagram
preliminary 40 am29lv160b ac characteristics alternate ce# controlled erase/program operations notes: 1. not 100% tested. 2. see the erase and programming performance section for more information. parameter 80r 90 120 jedec std description unit t avav t wc write cycle time (note 1) min 80 90 120 ns t avel t as address setup time min 0 ns t elax t ah address hold time min 45 45 50 ns t dveh t ds data setup time min 35 45 50 ns t ehdx t dh data hold time min 0 ns t oes output enable setup time min 0 ns t ghel t ghel read recovery time before write (oe# high to we# low) min 0 ns t wlel t ws we# setup time min 0 ns t ehwh t wh we# hold time min 0 ns t eleh t cp ce# pulse width min 35 35 50 ns t ehel t cph ce# pulse width high min 30 ns t whwh1 t whwh1 programming operation (note 2) byte typ 9 s word typ 11 t whwh2 t whwh2 sector erase operation (note 2) typ 0.7 sec
preliminary am29lv160b 41 ac characteristics t ghel t ws oe# ce# we# reset# t ds data t ah addresses t dh t cp dq7# d out t wc t as t cph pa data# polling a0 for program 55 for erase t rh t whwh1 or 2 ry/by# t wh pd for program 30 for sector erase 10 for chip erase 555 for program 2aa for erase pa for program sa for sector erase 555 for chip erase t busy notes: 1. pa = program address, pd = program data, dq7# = complement of the data written to the device, d out = data written to the device. 2. figure indicates the last two bus cycles of the command sequence. 3. word mode address used as an example. 21358f-28 figure 24. alternate ce# controlled write operation timings
preliminary 42 am29lv160b erase and programming performance notes: 1. typical program and erase times assume the following conditions: 25 c, 3.0 v v cc , 1,000,000 cycles. additionally, programming typicals assume checkerboard pattern. 2. under worst case conditions of 90c, v cc = 2.7 v, 1,000,000 cycles. 3. the typical chip programming time is considerably less than the maximum chip programming time listed, since most bytes program faster than the maximum program times listed. 4. in the pre-programming step of the embedded erase algorithm, all bytes are programmed to 00h before erasure. 5. system-level overhead is the time required to execute the two- or four-bus-cycle sequence for the program command. see table 9 for further information on command definitions. 6. the device has a minimum erase and program cycle endurance of 1,000,000 cycles. latchup characteristics includes all pins except v cc . test conditions: v cc = 3.0 v, one pin at a time. tsop and so pin capacitance notes: 1. sampled, not 100% tested. 2. test conditions t a = 25c, f = 1.0 mhz. data retention parameter typ (note 1) max (note 2) unit comments sector erase time 0.7 15 s excludes 00h programming prior to erasure (note 4) chip erase time 25 s byte programming time 9 300 s excludes system level overhead (note 5) word programming time 11 360 s chip programming time (note 3) byte mode 18 54 s word mode 12 36 s description min max input voltage with respect to v ss on all pins except i/o pins (including a9, oe#, and reset#) C1.0 v 12.5 v input voltage with respect to v ss on all i/o pins C1.0 v v cc + 1.0 v v cc current C100 ma +100 ma parameter symbol parameter description test setup typ max unit c in input capacitance v in = 0 6 7.5 pf c out output capacitance v out = 0 8.5 12 pf c in2 control pin capacitance v in = 0 7.5 9 pf parameter test conditions min unit minimum pattern data retention time 150 c 10 years 125 c 20 years
preliminary am29lv160b 43 physical dimensions* ts 04848-pin standard tsop (measured in millimeters) * for reference only. bsc is an ansi standard for basic space centering. tsr04848-pin reverse tsop (measured in millimeters) * for reference only. bsc is an ansi standard for basic space centering. 48 25 1 24 18.30 18.50 19.80 20.20 11.90 12.10 0.05 0.15 0.50 bsc 0.95 1.05 16-038-ts48-2 ts 048 dt95 8-8-96 lv pin 1 i.d. 1.20 max 0.50 0.70 0.10 0.21 0.25mm (0.0098") bsc 0? 5? 0.08 0.20 48 25 1 24 18.30 18.50 19.80 20.20 11.90 12.10 seating plane 0.05 0.15 0.50 bsc 0.95 1.05 16-038-ts48 tsr048 dt95 8-8-96 lv pin 1 i.d. 1.20 max 0.50 0.70 0.10 0.21 0.25mm (0.0098") bsc 0? 5? 0.08 0.20
preliminary 44 am29lv160b physical dimensions fgc48-ball fine-pitch ball grid array (fbga) 8 x 9 mm (measured in millimeters) 7.80 8.20 8.80 9.20 datum b datum a index 0.025 chamfer 0.15 m z b m 0.15 m z b m 5.60 bsc 0.40 4.00 bsc 0.08 m za b 0.10 z 0.25 0.45 0.80 detail a 0.20 z detail a 1.20 max 0.40 0.08 (48x) 0.40 16-038-fgc-2 eg137 12-2-97 lv
preliminary am29lv160b 45 physical dimensions so 04444-pin small outline package (measured in millimeters) 44 23 1 22 13.10 13.50 15.70 16.30 1.27 nom. 28.00 28.40 2.17 2.45 0.35 0.50 0.10 0.35 2.80 max. seating plane 16-038-so44-2 so 044 df83 8-8-96 lv 0.10 0.21 0.60 1.00 0? 8? end view side view top view
preliminary 46 am29lv160b revision summary for am29lv160b revision f distinctive characteristics changed typical read and program/erase current spec- ifications. device now has a guaranteed minimum endurance of 1,000,000 write cycles. figure 1, in-system sector protect/unprotect algorithm corrected a6 to 0, changed wait specification to 150 s on sector protect and 15 ms on sector unprotect. dc characteristics changed typical read and program/erase current spec- ifications. ac characteristics alternate ce# controlled erase/program operations: changed t cp to 35 ns for 70r, 80, and 90 speed options. erase and programming performance device now has a guaranteed minimum endurance of 1,000,000 write cycles. physical dimensions corrected dimensions for package length and width in fbga illustration (standalone data sheet version). revision f+1 table 9, command definitions corrected the byte-mode address in the sixth write cycle of the chip erase command sequence to aaah. revision f+2 figure 1, in-system sector protect/unprotect algorithms in the sector protect algorithm, added a reset plscnt=1 box in the path from protect another sec- tor? back to setting up the next sector address. dc characteristics changed i cc1 test conditions and note 1 to indicate that oe# is at v ih for the listed current. ac characteristics erase/program operations; alternate ce# controlled erase/program operations: corrected the notes refer- ence for t whwh1 and t whwh2 . these parameters are 100% tested. corrected the note reference for t vcs . this parameter is not 100% tested. temporary sector unprotect table added note reference for t vidr . this parameter is not 100% tested. figure 23, sector protect/unprotect timing diagram a valid address is not required for the first write cycle; only the data 60h. erase and programming performance in note 2, the worst case endurance is now 1 million cy- cles. trademarks copyright ? 1998 advanced micro devices, inc. all rights reserved. amd, the amd logo, and combinations thereof are registered trademarks of advanced micro devices, inc. expressflash is a trademark of advanced micro devices, inc. product names used in this publication are for identification purposes only and may be trademarks of their respective companies .

▲Up To Search▲

Price & Availability of AM29F160BB-120WCC

	To Download AM29F160BB-120WCC Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .